docs(schema-aware-routing): document OpenRouter as alternative provider#273
Conversation
Add OpenRouter as a first-class documented option alongside OpenAI direct in the schema-aware-routing recipe. Users who followed docs/01-getting-started.md Step 4 already have OpenRouter configured, so they no longer need to set up a separate OpenAI account just for this recipe. Changes: - README.md: Prerequisites line updated to call out both paths - README.md Step 2: Two concrete options — full copy-paste code for OpenAI direct (Option A) and OpenRouter (Option B) with key differences explained - index.ts: JSDoc on extractMetadata() and getEmbedding() updated to show both endpoint URLs and model strings - metadata.json: requires.services updated to reflect both providers No code logic, .env files, or SQL changed — pure documentation.
|
Hey @jjshanks — welcome to Open Brain Source! 👋 Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what. Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days. If you have questions, check out CONTRIBUTING.md or open an issue. |
alanshurafa
added
area: recipes
|
Thanks for the contribution. Documenting both provider options (OpenAI direct and OpenRouter) for the schema-aware-routing recipe is a useful addition and matches the canonical OB1 setup, which supports either. Small, additive change. One note for the maintainer: #273 and #310 both modify — Alan (community reviewer; non-binding) |
2 participants
Fixes #266
Contribution Type
/recipes)/schemas)/dashboards)/integrations)/skills)What does this do?
Adds OpenRouter as a first-class documented alternative alongside OpenAI direct in the
schema-aware-routingrecipe. Users who followeddocs/01-getting-started.mdStep 4 already have an OpenRouter account and key configured, so they no longer need to set up a separate OpenAI account just for this recipe. Step 2 now presents two copy-paste options (OpenAI direct and OpenRouter), JSDoc hints inindex.tscover both providers, andmetadata.jsonis updated to reflect both paths. This is a pure documentation change — no logic,.env, or SQL edits.Requirements
No new requirements. The recipe still needs:
@supabase/supabase-jsNo new dependencies, skills, or primitives.
Checklist